Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0856

reference: 463-tree-1
name: 0856
tree-preservation-order: undefined
463-tpo-1
uprn
address-text
point: POINT (-1.026193 50.884492)
geometry: MULTIPOLYGON (((-1.026122 50.884485,-1.026125 50.884499,-1.026135 50.884511,-1.026150 50.884521,-1.026170 50.884528,-1.026192 50.884530,-1.026214 50.884528,-1.026234 50.884522,-1.026250 50.884512,-1.026260 50.884500,-1.026264 50.884486,-1.026261 50.884472,-1.026251 50.884459,-1.026235 50.884449,-1.026216 50.884443,-1.026194 50.884440,-1.026172 50.884442,-1.026152 50.884449,-1.026136 50.884458,-1.026126 50.884471,-1.026122 50.884485)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL